…23656)

* Derive repo identity from git remote instead of directory basename

* Add changelog

* Drop leading underscore from GIT_REMOTE_PATTERNS module constant

* Consolidate URL-parsing tests into Repository identity tests

* Keep GitHubManager pointed at DataDog regardless of origin

Codex review on PR #23656 caught a regression: deriving the org from the
git remote URL means fork users would have their GitHubManager target
their fork's API (e.g. `alice/integrations-core`), where the PRs,
release labels and validation comments don't live.

Revert that piece: `GitHubManager.repo_id` is back to `f'DataDog/{full_name}'`.
The worktree fix still stands because `full_name` itself is now derived
from the origin URL, so worktrees and forks both resolve to the right
repo name. `Repository.org` and `DEFAULT_ORG` are dropped since nothing
else consumed them.

* Migrate validate jmx-metrics from datadog_checks_dev to ddev

* Add changelog

* Apply formatter

* Fix mypy union-attr errors in _duplicate_bean_check

* Pass 'all' sentinel to iter() so the no-arg and 'all' branches actually validate every JMX integration

An empty selection tuple makes IntegrationRegistry.__finalize_selection
fall back to its 'changed roots' path, which iterates zero (or only
changed) integrations instead of all of them. Use ('all',) so the
finalizer returns set(), producing the intended full iteration.

Add a parametrized regression test that creates three fake JMX checks
and asserts both 'ddev validate jmx-metrics' and
'ddev validate jmx-metrics all' validate all three.

* Update otel_host_metrics_dashboard.json

Applies semantic_mode native because we strictly want this to include the OTel host metrics only. 

Also explicitly queries system metrics with and without otel prefixes for backwards compatibility.

* fix formatting

* Remove pause_auto_refresh from OTel host metrics dashboard

The datadog-assets validate-dashboards schema rejects this property
(Additional properties are not allowed).

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Pablo Baeyens <pablo.baeyens@datadoghq.com>